Dual rotor, rotary wing aircraft

ABSTRACT

An aircraft is provided and includes an airframe, an extending tail, a counter rotating, coaxial main rotor assembly including an upper rotor assembly and a lower rotor assembly, a translational thrust system positioned at the extending tail, the translational thrust system providing translational thrust to the airframe, at least one sensor and at least one inertial measurement unit (IMU) to sense current flight conditions of the aircraft, an interface to execute controls of a main rotor assembly in accordance with control commands and at least one flight control computer (FCC) to issue the control commands. The at least one FCC includes a central processing unit (CPU) and a memory having logic and executable instructions stored thereon, which, when executed, cause the CPU to issue the control commands based on the current flight conditions and a result of an execution of the logic for the current flight conditions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. provisional patent application Ser. No. 62/058,424, filed Oct. 1, 2014, the entire contents of which are incorporated herein by reference.

BACKGROUND

The subject matter disclosed herein relates generally to rotary wing aircraft and, more particularly, to a dual rotor, rotary wing aircraft.

A dual, rotary wing aircraft generally includes an airframe with an extending tail. A dual, counter rotating, coaxial main rotor assembly is located at the airframe and rotates about a main rotor axis. The main rotor assembly is driven by a power source, for example, one or more engines via a gearbox, such that an upper rotor assembly is driven in a first direction (e.g., counter-clockwise) about the main rotor axis and a lower rotor assembly is driven in a second direction about the main rotor axis opposite to the first direction (i.e., counter rotating rotors). Each of the upper rotor assembly and the lower rotor assembly includes a plurality of rotor blades secured to a rotor hub. The aircraft may further include a translational thrust system located at the extending tail to provide translational thrust (forward or rearward).

Due to various factors, including the complexity of dual, rotary wing aircrafts, pilot workload during grounded and in-flight operations can be extremely high. The pilot must be concerned with current flight conditions, the state of the one or more engines, the orientation of the aircraft and the working condition of the main rotor assembly and the translational thrust system.

SUMMARY

According to an aspect, an aircraft is provided and includes an airframe, an extending tail, a counter rotating, coaxial main rotor assembly including an upper rotor assembly and a lower rotor assembly, a translational thrust system positioned at the extending tail, the translational thrust system providing translational thrust to the airframe, at least one sensor and at least one inertial measurement unit (IMU) to sense current flight conditions of the aircraft, an interface to execute controls of a main rotor assembly in accordance with control commands and at least one flight control computer (FCC) to issue the control commands. The at least one FCC includes a central processing unit (CPU) and a memory having logic and executable instructions stored thereon. When executed, the executable instructions cause the CPU to issue the control commands based on the current flight conditions and a result of an execution of the logic for the current flight conditions.

In accordance with additional or alternative embodiments, the current flight conditions include a speed of the aircraft and wind conditions.

In accordance with additional or alternative embodiments, the interface includes a rotor interface, which is coupled to upper and lower rotor assemblies of the main rotor assembly and configured to independently control collective and cyclic pitching thereof.

In accordance with additional or alternative embodiments, the logic includes at least one of a fly-by-wire (FBW) or smart-control database and an algorithm.

In accordance with additional or alternative embodiments, the FBW or smart-control database indexes the speed of the aircraft to control commands for setting respective collective pitching of the upper and lower rotor assemblies, and the algorithm computes control commands for setting respective collective pitching of the upper and lower rotor assemblies.

According to another aspect, a fly-by-wire (FBW) or smart-control system of a coaxial, counter-rotating aircraft is provided. The FBW or smart-control system includes at least one sensor and at least one inertial measurement unit (IMU) to sense current flight conditions of the aircraft, interfaces to respectively execute controls of a main rotor assembly, a translational thrust system, controllable surfaces and an engine in accordance with respective control commands and at least one flight control computer (FCC) to issue the control commands. The at least one FCC includes a central processing unit (CPU) and a memory having logic and executable instructions stored thereon. When executed, the executable instructions cause the CPU to issue the control commands based on the current flight conditions and a result of an execution of the logic for the current flight conditions.

In accordance with additional or alternative embodiments, the current flight conditions include a speed of the aircraft and wind conditions.

In accordance with additional or alternative embodiments, the interfaces include a rotor interface, which is coupled to upper and lower rotor assemblies of the main rotor assembly and configured to independently control collective and cyclic pitching thereof, a translational thrust interface, which is coupled to the translational thrust system to control collective pitch or a power setting of the translational thrust system, an elevator and rudder actuation interface, which is coupled to active elevators and active rudders to control an angling thereof, an engine interface, which is coupled to the engine to control an RPM thereof and a propeller clutch interface which is coupled to the propeller clutch to control the propeller engagement state.

In accordance with additional or alternative embodiments, the logic includes at least one of an FBW or smart-control database and an algorithm.

In accordance with additional or alternative embodiments, the FBW or smart-control database indexes the speed of the aircraft to control commands for setting respective collective pitching of the upper and lower rotor assemblies.

In accordance with additional or alternative embodiments, the algorithm computes control commands for setting respective collective pitching of the upper and lower rotor assemblies.

In accordance with additional or alternative embodiments, the logic generates differential collective pitch control commands for setting respective collective pitching of the upper and lower rotor assemblies in an event the speed of the aircraft is below a first speed, a mix of differential collective and differential cyclic pitch control commands for setting respective collective and cyclic pitching of the upper and lower rotor assemblies in an event the speed of the aircraft is above the first speed and below a second speed and angle control commands for setting an angling of the active rudders in an event the speed of the aircraft is above the second speed.

In accordance with additional or alternative embodiments, the logic generates envelope control commands for applying respective control envelopes to the upper and lower rotor assemblies.

In accordance with additional or alternative embodiments, the logic generates a single control command for setting engine RPMs and a pitching of the translational thrust system.

In accordance with additional or alternative embodiments, the logic generates a control command for setting an RPM schedule to maintain a predefined mach number of the upper and lower rotor assemblies.

According to another aspect, a method of operating a fly-by-wire (FBW)_or smart-control system of an aircraft is provided. The method includes sensing current flight conditions of the aircraft by at least one sensor and at least one inertial measurement unit (IMU), executing controls of a main rotor assembly in accordance with control commands and issuing the control commands from a central processing unit (CPU) of at least one flight control computer (FCC) based on the current flight conditions and a result of an execution of logic for the current flight conditions.

In accordance with additional or alternative embodiments, the sensing includes sensing a speed of the aircraft and wind conditions.

In accordance with additional or alternative embodiments, the executing of the controls of the main rotor assembly includes independently controlling collective and cyclic pitching of upper and lower rotor assemblies.

In accordance with additional or alternative embodiments, the logic includes at least one of an FBW or smart-control database and an algorithm.

In accordance with additional or alternative embodiments, the method further includes indexing the speed of the aircraft to control commands for setting respective collective pitching of the upper and lower rotor assemblies by reference to the FBW or smart-control database and computing control commands for setting respective collective pitching of the upper and lower rotor assemblies by reference to the algorithm.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings wherein like elements are numbered alike in the several FIGURES:

FIG. 1 depicts a rotary wing aircraft in an exemplary embodiment;

FIG. 2 is a perspective view of a rotary wing aircraft in an exemplary embodiment;

FIG. 3 is a perspective view of a gear train for a rotary wing aircraft in an exemplary embodiment;

FIG. 4 is a perspective view of a gearbox and translational thrust system in an exemplary embodiment;

FIG. 5 is a perspective view of a rotor hub fairing in an exemplary embodiment;

FIG. 6A depicts a flight control system in an exemplary embodiment;

FIG. 6B depicts a portion of the flight control system of FIG. 6A; and

FIG, 7 depicts a flight maneuver in an exemplary embodiment.

DETAILED DESCRIPTION

FIG. 1 depicts an embodiment of a rotary wing, vertical takeoff and land (VTOL) aircraft 10. The aircraft 10 includes an airframe 12 with an extending tail 14. A dual, counter rotating, coaxial main rotor assembly 18 is located at the airframe 12 and rotates about a main rotor axis, A. The main rotor assembly 18 is driven by a power source, for example, one or more engines 24 via a gearbox 26. The main rotor assembly 18 includes an upper rotor assembly 28 driven in a first direction (e.g., counter-clockwise) about the main rotor axis, A, and a lower rotor assembly 32 driven in a second direction (e.g., clockwise) about the main rotor axis, A, opposite to the first direction (i.e., counter rotating rotors). Each of the upper rotor assembly 28 and the lower rotor assembly 32 includes a plurality of rotor blades 36 secured to a rotor hub 38. In some embodiments, the aircraft 10 further includes a translational thrust system 40 located at the extending tail 14 to provide translational thrust (forward or rearward) for aircraft 10.

Any number of blades 36 may be used with the rotor assembly 18. The rotor assembly 18 includes a rotor hub fairing 37 generally located between and around the upper and lower rotor assemblies such that the rotor hubs 38 are at least partially contained therein. The rotor hub fairing 37 provides drag reduction. Rotor blades 36 are connected to the upper and lower rotor hubs 38 in a hingeless manner, also referred to as a rigid rotor system. Although a particular aircraft configuration is illustrated in this non-limiting embodiment, other rotary-wing aircraft will also benefit from embodiments. Although, the dual rotor system is depicted as coaxial, embodiments include dual rotor aircraft having non-coaxial rotors.

The translational thrust system 40 includes a propeller 42 connected to and driven by the engine(s) 24 via the gearbox 26. The translational thrust system 40 may be mounted to the rear of the airframe 12 with a translational thrust axis, T, oriented substantially horizontal and parallel to the aircraft longitudinal axis, L, to provide thrust for high-speed flight. The translational thrust axis, T, corresponds to the axis of rotation of propeller 42. While shown in the context of a pusher-prop configuration, it is understood that the propeller 42 could also be more conventional puller prop or could be variably facing so as to provide yaw control in addition to or instead of translational thrust. It should be understood that any such system or other translational thrust systems may alternatively or additionally be utilized. Alternative translational thrust systems may include different propulsion forms, such as a jet engine.

Referring to FIG. 2, translational thrust system 40 includes a propeller 42 and is positioned at a tail section 41 of the aircraft 10. Propeller 42 includes a plurality of blades 47. In exemplary embodiments, the pitch of propeller blades 47 may be altered to change the direction of thrust (e.g., forward or rearward). The tail section 41 includes active elevators 43 and active rudders 45 as controllable surfaces.

Shown in FIG. 3 is a perspective view of portions of main rotor assembly 18 and gearbox 26. The gearbox 26 includes an upper bull gear 44 rotates about the main rotor axis, A, and connected to the lower rotor assembly 32 via a lower rotor shaft 46 extending along the main rotor axis, A. A lower bull gear 48 rotates about the main rotor axis, A, and is connected to the upper rotor assembly 28 via an upper rotor shaft 50 extending along the main rotor axis, A, and through an interior of the lower rotor shaft 46. Torque and rotational speed are provided to the gearbox 26 via input shaft 52 that transmits the torque and rotational speed from the engine(s) 24 to an input bevel gear 54 disposed at an input bevel shaft 56 of the gearbox 26 via an input bevel pinion 104. In some embodiments, the input bevel shaft 56 rotates about an input bevel shaft axis 58 parallel to the main rotor axis A. The propeller 42 is driven by a propeller output shaft 106 driven by a propeller output gear 62 disposed at a quill shaft 102, or an extension of input bevel shaft 56. Transfer from the propeller output gear 62 is achieved via connection with a propeller output pinion 60 at the propeller output shaft 106. To transfer torque from the input bevel shaft 56 to the lower rotor assembly 32 and the upper rotor assembly 30, the gearbox 26 includes a torque split gear reduction stage 64. While shown with the propeller output shaft 106 driven by the propeller output gear 62, it is understood that such elements could be removed where the propeller 42 is not used or is separately driven.

Referring to FIG. 4, the main rotor assembly 18 is driven about the axis of rotation, A, through a main gearbox (MGB) 26 by a multi-engine powerplant system 24, having two engine packages ENG1, ENG2 in the example in FIG. 4. The multi-engine powerplant system 24 generates the power available for flight operations and couples such power to the main rotor assembly 18 and the translational thrust system 40 through the MGB 26. The MOB 26 may be interposed between the powerplant system 24, the main rotor assembly 18 and the translational thrust system 40.

A portion of the drive system downstream of the MGB 26 includes a combined gearbox 90 (also referred to as a clutch). The combined gearbox 90 selectively operates as a clutch and a brake for operation of the translational thrust system 40 with the MOB 26. The combined gearbox 90 also operates to provide a rotor brake function for the main rotor assembly 18.

The combined gearbox 90 generally includes an input 92 and an output 94 generally defined along an axis parallel to rotational axis, T. The input 92 is generally upstream of the combined gearbox 90 relative the MOB 26 and the output 94 is downstream of the combined gearbox 90 and upstream of the pusher propeller system 40 (FIG, 2), The combined gearbox 90 may be categorized by the technique used to disengage-engage (e.g., clutch) or stop (e.g., brake) the load such as friction, electromagnetic, mechanical lockup, etc., and by the method used to actuate such as mechanical, electric, pneumatic, hydraulic, self-activating, etc. It should be understood that various combined gearbox 90 systems may be utilized to include but not to be limited to mechanical, electrically, hydraulic and various combinations thereof.

Referring to FIG. 5, an exemplary rotor hub fairing 37 is shown. Rotor hub fairing 37 is illustrated having generally elliptical, in cross-section, upper and lower hub fairings 111 and 112, and an airfoil-type shape (in horizontal cross-section) for the shaft fairing 103. The airfoil shape of the shaft fairing 103 includes a leading edge 114, and a trailing edge 115 aft of the upper and lower fairings 111, 112. The airfoil shape of the shaft fairing 103 additionally includes a chord (not shown) that connects the leading and trailing edges 114, 115 of the airfoil. In one embodiment, the airfoil shape, including the upper surface 116 and the lower surface 117, is symmetrical about a plane extending along the length of the shaft fairing 103 and containing the axis of rotation, A. As noted above, the upper and lower rotor hubs 38 may be positioned, at least partially, in the upper and lower fairings 111, 112.

Portions of the aircraft 10 are controlled by a flight control system 120 illustrated in FIGS. 6A and 6B. In one embodiment, the flight control system 120 is a fly-by-wire (FBW) control system. In a FBW control system there is no direct mechanical coupling between a pilot's controls and movable components of aircraft 10. Instead of using mechanical linkages, a FBW control system includes a plurality of sensors and/or inertial measurement units (IMUs) 122 (hereinafter referred to as “sensors 122”) which can sense various flight conditions of the aircraft 10, such as the speed of the aircraft 10, wind speeds surrounding the aircraft 10, the position of controlled elements and generate electrical signals proportional to the sensed position. The sensors 122 may also be used directly and indirectly to provide a variety of aircraft state data to a flight control computer (FCC) 124. The FCC 124 may also receive inputs 126 as control commands from various sources. For instance, the inputs 126 can be pilot inputs, auto-pilot inputs, navigation system based inputs, or any control inputs from one or more control loops executed by the FCC 124 or other subsystems. In response to inputs from the sensors 122 and inputs 126, the FCC 124 transmits signals to various subsystems of the aircraft 10.

Flight control system 120 may include a rotor interface 128 configured to receive commands from the FCC 124 and control one or more actuators, such as a mechanical-hydraulic or electric actuators, for the upper rotor assembly 28 and lower rotor assembly 32. In an embodiment, inputs 126 including cyclic, collective, pitch rate, and throttle commands that may result in the rotor interface 128 driving the one or more actuators to adjust upper and lower swashplate assemblies (not depicted) for pitch control of the upper rotor assembly 28 and lower rotor assembly 32. Alternatively, pitch control can be performed without a swashplate assemblies using individual blade control (IBC) in the upper rotor assembly 28 and lower rotor assembly 32. The rotor interface 128 can manipulate the upper rotor assembly 28 and lower rotor assembly 32 independently. This allows different collective and cyclic commands to be provided to the upper rotor assembly 28 and lower rotor assembly 32.

Flight control system 120 may include a translational thrust interface 130 configured to receive commands from the FCC 124 to control one or more actuators, such as a mechanical-hydraulic or electric actuators, for the control of the translational thrust system 40. In an embodiment, inputs 126 may result in the translational thrust interface 130 controlling speed of propeller 42, altering the pitch of propeller blades 47 (e.g., forward or rearward thrust), altering the direction of rotation of propeller 42, controlling gearbox 90 to employ a clutch to engage or disengage the propeller 42, etc.

Flight control system 120 may include an elevator and rudder actuation interface 132. The elevator and rudder actuation interface 132 is configured to receive commands from the FCC 124 to control one or more actuators, such as a mechanical-hydraulic or electric actuators, for the active elevator 43 and/or active rudders 45 of FIG. 2. In an embodiment, inputs 126 include an elevator pitch rate command for the elevator and rudder actuation interface 132 to drive the one or more actuators for pitch control of the active elevators 43 of FIG. 2. In an embodiment, inputs 126 include a rudder command for the elevator and rudder actuation interface 132 to drive the one or more actuators for positional control of the active rudders 45 of FIG. 2.

Flight control system 120 may include an engine interface 133. The engine interface 133 is configured to receive commands from the FCC 124 to control engine(s) 24. In an embodiment, inputs 126 include a throttle command from the pilot to adjust the RPM of engine(s) 24. FCC 124 may also send commands to engine interface 133 to control the engine(s) in certain predefined operating modes (e.g., quiet mode).

The FCC 124 includes a processing system 134 that applies models and control laws to augment commands based on aircraft state data. The processing system 134 includes processing circuitry 136 (i.e., a central processing unit), memory 138, and an input/output (I/O) interface 140. The processing circuitry 136 may be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array, and is generally referred to as central processing unit (CPU) 136. The memory 138 can include volatile and non-volatile memory, such as random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic, or any other computer readable storage medium onto which data and control logic as described herein are stored. Therefore, the memory 138 is a tangible storage medium where instructions executable by the processing circuitry 136 are embodied in a non-transitory form. The I/0 interface 140 can include a variety of input interfaces, output interfaces, communication interfaces and support circuitry to acquire data from the sensors 122, inputs 126, and other sources (not depicted) and communicate with the rotor interface 128, the translation thrust interface 130, tail faring interface 132, engine interface 133, and other subsystems (not depicted).

In exemplary embodiments, the rotor interface 128, under control of the FCC 124, can control the upper rotor assembly 28 and lower rotor assembly 32 to pitch in different magnitudes and/or different directions at the same time. This includes differential collective, where the upper rotor assembly 28 has a collective pitch different than the collective pitch of the lower rotor assembly 32, in magnitude and/or direction. Differential pitch control also includes differential cyclic pitch control, where the upper rotor assembly 28 has a cyclic pitch different than the cyclic pitch of the lower rotor assembly 32, in magnitude, axis of orientation (e.g., longitudinal or lateral) and/or direction. The differential collective and the differential cyclic pitch control may be accomplished using independently controlled swashplates in the upper rotor assembly 28 and lower rotor assembly 32. Alternatively, differential collective and the differential cyclic pitch control may be accomplished using individual blade control in the upper rotor assembly 28 and lower rotor assembly 32.

The ability to independently control the pitch of the upper rotor assembly 28 and lower rotor assembly 32 allows the lower rotor assembly 32 to be adjusted due to its position beneath the upper rotor assembly 28. The lower rotor assembly 32 is located in the downwash of the upper rotor assembly 28. To accommodate for this, the lower rotor assembly 32 may have a collective pitch that differs from the collective pitch of the upper rotor assembly 28.

In the case of traditional helicopters, as the forward velocity of the aircraft increases, the velocity of the retreating blade relative to the airflow decreases. This causes a stall region to arise at the root of the retreating blade and expand towards to distal end of the blade as speed increases. As this stall region increases, the overall lift vector of the aircraft shifts from the center of the aircraft towards the advancing blade which is providing the majority of lift for the aircraft. This imbalance of lift creates an unstable rolling moment on the aircraft which is stabilized by a combination of reducing forward flight and blade flapping, which reduces overall aircraft lift. With a dual rotor aircraft, such as aircraft 10, the counter rotating rotor heads balance out the torque generated by each rotor head and also balances the lift generated by each advancing blade without the need for blade flapping or reducing the speed of the aircraft. This is made possible by the rigid rotor system. With two rigid rotors, the roll moments cancel at the main rotor shaft.

The use of upper rotor assembly 28 and lower rotor assembly 32 allows the pre-cone angle to be set on each individual rotor to reduce bending stress on the blades. In a hinged rotor design, the hinges will naturally go to an angle to reduce bending stress. On a rigid rotor aircraft, such as aircraft 10, there is no hinge, so the pre-cone angle is set to avoid the extra stress attributed to the bending moment. A useful pre-cone angle is one where the centrifugal force of the blade pulling out matches the lift of the blade up. Due to the independent nature of the upper rotor assembly 28 and lower rotor assembly 32, differential pre-cone is used in aircraft 10. Differential pre-cone refers to the fact that the upper rotor assembly 28 and lower rotor assembly 32 have different pre-cone angles. The different pre-cone angles for the upper rotor assembly 28 and lower rotor assembly 32 help maintain tip clearance. In an exemplary embodiment, the pre-angle on the upper rotor assembly 28 is about 3 degrees and the pre-cone angle on the lower rotor assembly 32 is about 2 degrees.

Aircraft 10 is operational in a variety of modes, including take-off, cruise, landing, etc. Cruise mode refers to generally horizontal flight. During cruise, aircraft 10 can reach speeds of above about 200 knots, with speed reaching up to about 250 knots. During cruise mode, the main rotor assembly 18 provides the majority of lift for the aircraft. In exemplary embodiments, the main rotor assembly 18 provides greater than about 85% of the lift during cruise mode.

Aircraft 10 may assume various acoustic modes, depending on the flight state. FCC 124 may control RPM of engines 24, RPM of propeller 42, and clutch 90 (i.e., a propeller clutch interface) to engage or disengage the propeller 42 to assume different noise levels. For example, at take-off noise may not be a concern, and there would be no changes in aircraft operation to adjust the noise level. As the aircraft approaches a target, it may be desirable to disengage the propeller 42 using clutch 90 and/or reduce RPM of engines 24 to reduce the noise produced by aircraft 10. The propeller 42 may be disengaged at various other flight states (e.g., high speed) to reduce noise. The RPM of the main rotor assembly 18 and RPM of propeller 42 may be independently controlled (e.g., through clutch 90).

The pilot may enter separate commands to reduce aircraft noise, for example, disengaging the propeller 42 and reducing engine RPM as separate inputs. Alternatively, the pilot may select a reduced noise mode (e.g., quiet mode) through single input, and the FCC 124 controls the various aircraft interfaces to achieve the desired mode. For example, the pilot may select a reduced noise mode at input 126, and the FCC automatically disengages the propeller 42 and/or reduces the engine 24 RPM without further demand on the pilot.

The use of the translational thrust system 40 allows the aircraft 10 to move forward or rearward (depending on the pitch of the propeller blades) independent of the pitch attitude of the aircraft. Cyclic is used to adjust the pitch attitude (nose up, nose down or level) of the aircraft while the translational thrust system 40 provides forward and rearward thrust.

The motor rotor assembly 18 system and the translational thrust system 40 are connected through the main gear box 26. A gear ratio of main gear box 26 is selected so as to keep propeller 42 at a high efficiency and suitable noise level during cruise mode. The gear ratio of main gear box 26 dictates the ratio of the rotor speed of main rotor assembly 18 to propeller speed of propeller 42.

Embodiments of aircraft 10 provide the pilot with increased situational awareness by allowing the aircraft attitude (e.g., the angle of longitudinal axis, L, relative to horizontal) to be adjusted by cyclic pitch of the main rotor assembly 18 and the forward and rearward thrust to be controlled by the translational thrust system 40. This allows a variety of flight modes to be achieved, which allows the pilot to be more aware of their surroundings. Aircraft 10 can take off at a horizontal attitude (e.g., axis L is horizontal), which also may be referred to as vertical take-off. Aircraft 10 may also fly forward or cruise with the nose angled upwards or downwards. Aircraft 10 can hover with the nose angled upwards or downwards or level. Aircraft 10 can also land substantially parallel to a non-horizontal or sloped surface by adjusting the attitude of the aircraft using cyclic pitch of the main rotor assembly 18. The use of main rotor assembly 18 for aircraft attitude and the translational thrust system 40 for thrust allows aircraft 10 to assume a variety of trim states.

Embodiments provide independent control of the active elevators 43 and/or active rudders 45 as controllable surfaces in the tail section 41. The elevator surfaces 43 may be controlled independently by the FCC 124 through the tail faring interface 132. The rudder surfaces 45 may be controlled independently by the FCC 124 through the tail faring interface 132.

The configuration of aircraft 10 and the controlled afforded by FCC 124 allows aircraft 10 to provide a high bank angle capability at high speeds. For example, in an exemplary embodiment, aircraft 10 can achieve a bank angle of about 60 degrees at about 210 knots.

Aircraft 10 may make use of longitudinal lift offset in trim to compensate for rotor-on-rotor aerodynamic interaction between the upper rotor assembly 28 and lower rotor assembly 32. Aircraft 10 may adjust differential longitudinal cyclic as a function of operational states of the aircraft (e.g., take-off, cruise, land, etc.). Differential longitudinal cyclic refers to upper rotor assembly 28 and lower rotor assembly 32 having different cyclic pitch along the longitudinal axis of the aircraft. Differential longitudinal cyclic may also be used to generate yaw moments. Lift offset may be used to control aircraft, where lateral lift offset adjusts roll and longitudinal lift offset adjusts pitch.

FCC 124 may control RPM of engine(s) 24, RPM of propeller 42, and clutch 90 to engage or disengage the propeller 42 to assume different noise levels. For example, at take-off noise may not be a concern, and there would be no changes in aircraft operation to adjust the noise level. As the aircraft approaches a target, it may be desirable to disengage the propeller 42 using clutch 90 and/or reduce RPM of engines 24 to reduce the noise produced by aircraft 10. The propeller 42 may be disengaged at various other flight states (e.g., high speed) to reduce noise. The RPM of the main rotor assembly 18 and RPM of propeller 42 may be independently controlled (e.g., through clutch 90).

The pilot may enter separate commands to reduce aircraft noise, for example, disengaging the propeller 42 and reducing engine RPM as separate inputs. Alternatively, the pilot may select a reduced noise mode (e.g., quiet mode) through single input, and the FCC 124 controls the various aircraft interfaces to achieve the desired mode. For example, the pilot may select a reduced noise mode at input 126, and the FCC automatically disengages the propeller 42 and/or reduces the engine 24 RPM without further demand on the pilot.

Aircraft 10 provides the ability to approach a target and reverse thrust while maintaining an attitude directed at the target. FIG. 7 depicts aircraft 10 approaching a target 200. In a first state, 202, the aircraft 10 alters the pitch of blades 47 in propeller 42 to provide reverse thrust to bring the aircraft to a quick stop. At state 204, the main rotor assembly 18 and propeller 42 are controlled to pitch aircraft 10 towards target 200. At state 206, the propeller 42 is used to provide reverse thrust to move away from target 200 and climb, while still maintaining an attitude with the nose of aircraft 10 facing target 200.

The use of a dual rotor system and translational thrust allows aircraft 10 to eliminate the need for a variable angle between the main axis of rotation of the rotor system (e.g., axis A in FIG. 1) and aircraft longitudinal axis L. In conventional helicopters, the angle between the main axis of rotation of the rotor system and the aircraft longitudinal axis L varies. This is due to the fact that conventional helicopters lack a translational thrust system 40 for use during cruise mode, or forward flight. In a conventional helicopter, forward flight is provided through cyclic pitch, which causes the aircraft to point nose down. As this nose down orientation is undesirable beyond a certain angle, the angle between the main axis of rotation of the rotor system and the aircraft longitudinal axis L is adjusted to bring the nose upwards, while still in forward flight.

By contrast, aircraft 10, with translational thrust system 40, does not need to adjust the angle between the main axis of rotation of the rotor system (e.g., axis A in FIG. 1) and aircraft longitudinal axis L. The angle between the main axis of rotation of the rotor system (e.g., axis A in FIG. 1) and aircraft longitudinal axis L for aircraft 10 remains fixed during all flight modes, including take-off, cruise, landing, etc.

As shown in FIG. 1, the rotor assembly 18 includes a rotor hub fairing 37 generally located between and around the upper and lower rotor assemblies such that the rotor hubs 38 are at least partially contained therein. The rotor hub fairing 37 provides drag reduction. Referring to FIG, 5, an exemplary rotor hub fairing 37 is shown. Rotor hub fairing 37 is illustrated having generally elliptical, in cross-section, upper and lower hub fairings 111 and 112, and an airfoil-type shape (in horizontal cross-section) for the shaft fairing 103. The airfoil shape of the shaft fairing 103 includes a leading edge 114, and a trailing edge 115 aft of the upper and lower fairings 111, 112. The airfoil shape of the shaft fairing 103 additionally includes a chord (not shown) that connects the leading and trailing edges 114, 115 of the airfoil. In one embodiment, the airfoil shape, including the upper surface 116 and the lower surface 117, is symmetrical about a plane extending along the length of the shaft fairing 103 and containing the axis of rotation, A. As noted above, the upper and lower rotor hubs 38 may be positioned, at least partially, in the upper and lower fairings 111, 112.

The rotor hub fairing 37 is a sealed fairing, meaning there are few or no passages for air to travel through the interior of the rotor hub fairing 37. In conventional designs, control devices such as pushrods, are exposed near the rotor hubs. The surfaces of these components increase drag on the rotor assembly. The air gaps between various rotor structures (e.g., pushrods and main rotor shaft) also form areas of drag. The sealed rotor hub fairing 37 eliminates air pathways through the rotor hub structure, and eliminates drag associated with such air paths.

Another feature to reduce drag on the rotor hub is positioning the push rods for rotor control internal to the main rotor shaft. Referring to FIG. 3, pushrods for swashplates in the upper rotor assembly 28 and lower rotor assembly 32 are located internal to the lower rotor shaft 46 and upper rotor shaft 50. This prevents the pushrods from being exposed and increasing drag on the rotor hub. The use of a rigid rotor system aids in sealing the rotor hub faring 37.

Aircraft 10 may employ an active vibration control (AVC) system to reduce vibration in the airframe 12. The use of a dual rotor, rigid rotor system tends to produce significant vibration in the airframe 12 and its systems. FIG. 9 depicts an AVC system in an exemplary embodiment. An AVC controller 300 executes an AVC control process to reduce vibration in aircraft 10. AVC controller 300 may be implemented as part of flight control system 120, executed by FCC 124, or may be a separate controller. One or more sensors 302 are located in aircraft 10 to detect vibration. Sensors may be located in a wide variety of positions, including airframe 12, gearbox 26, tail section 14, on main rotor assembly 18, cockpit, etc. It is understood that these locations are exemplary, and the AVC sensors 302 may be located in any position. AVC actuators 304 generate a force to dampen vibration in aircraft 10, as known in the art. AVC actuators 304 may be located in any position in the aircraft.

In operation, AVC controller 300 receives vibration signals from the AVC sensors 302. AVC controller 300 provides control signals to the AVC actuators 304 to reduce the vibration sensed by the AVC sensors 302. Control signals to the AVC actuators 304 may vary in magnitude and frequency to cancel vibrations in aircraft 10. In an exemplary embodiment, AVC controller 300 operates in a feedback mode, where the control signals to AVC actuators 304 are adjusted in response to measured vibration from AVC sensors 302. In an alternate embodiment, AVC controller 300 does not actively measure vibration through AVC sensors 302. Rather, the AVC controller 300 obtains the rotor speed (e.g., through an RPM signal) and applies a control signal to the AVC actuators 304, in an open loop control mode.

As will be described below, a smart-control system may be provided for the aircraft 10. The FBW or smart-control system may include the sensors 122 to sense current flight conditions of the aircraft 10 and various interfaces. The various interfaces may include, but are not limited to, the rotor interface 128, the translational thrust interface 130, the elevator and rudder actuation interface 132, the engine interface 133 and a propeller clutch interface which is coupled to the propeller clutch to control the propeller engagement state and serve to respectively execute controls of the main rotor assembly 18, the translational thrust system 40, controllable surfaces, such as the active elevators 43 and the active rudders 45, and the one or more engines 24. Such control is executed in accordance with respective control commands.

The FBW or smart-control system further includes the FCC 124, which in these embodiments, is configured to issue the control commands to the interfaces. The FCC, as described above, includes the processing circuitry 136 and the memory 138. As shown in FIG. 6B, the memory 138 has logic and executable instructions stored thereon. The logic may be embodied as a smart-control database 1380 and/or as an algorithm 1381. When executed, the executable instructions cause the processing circuitry 136 to issue the control commands based on the current flight conditions and a result of an execution of the logic for the current flight conditions. Various embodiments related to the issuance of the control commands will be discussed below.

The use of independently controlled upper rotor assembly 28 and the lower rotor assembly 32, along with other control surfaces, provides the ability to control yaw using a variety of elements. For example, below a first speed (e.g., 40 knots) as sensed by the sensors 122, the FCC 124 issues control commands for setting differential collective pitch for yaw control to the rotor interface 128. Above the first speed but below a second speed (e.g., 80 knots), a mix of differential collective and differential cyclic may be used to control yaw. The differential cyclic may be applied along the longitudinal and/or lateral axes of the aircraft. Further, wind direction may be measured by the sensors 122 and used to adjust the differential cyclic about the longitudinal and/or lateral axes. Above the second speed (e.g., 80 knots), the active rudders 45 are used as controllable surfaces to control yaw. Here, the FCC 124 provides corresponding control commands to the elevator and rudder actuation interface 132 to control the rudders 45 to adjust yaw.

The use of active elevators 43, with independent control of a left elevator section and a right elevator section, provides for improved stability control. Flight control system 120 and the FCC 124 thus may perform mixing of collective pitches of the main rotor assembly 18 and an angle of the active elevators 43 to provide stability augmentation. In such cases, the FCC may issue the corresponding control commands to the rotor interface 128 and the elevator and rudder actuation interface 132.

The use of a dual rotor, main rotor assembly 18 allows improvements in control of main rotor assembly 18. Flight control system 120 may apply different control envelopes to the upper rotor assembly 28 and the lower rotor assembly 32. Flight control system 120 may impose different control ranges onto the upper rotor assembly 28 and the lower rotor assembly 32 including control elements such as prioritization, gain vs. differential, collective versus cyclic, etc. The upper rotor assembly 28 and the lower rotor assembly 32 may be independently controlled through the use of separate upper and lower swashplates. Alternatively, the upper rotor assembly 28 and the lower rotor assembly 32 may be independently controlled using individual blade control (IBC) techniques.

Aircraft 10 may employs a fly-by-wire (FBW) control system to reduce pilot work load. In an exemplary embodiment, FCC 124 determines the aircraft airspeed based on the readings of one or more of the sensors 122. The FCC 124 then adjusts the collective pitch of the upper rotor assembly 28 and the lower rotor assembly 32 in response to the sensed airspeed by sending appropriate control commands to the rotor interface 128. FCC 124 may use a look-up table in the FBW or smart-control database 1380 that indexes airspeed to collective pitch. Alternatively, FCC 124 may use the algorithm 1381 to compute the collective pitch based on airspeed. As noted above, the collective pitch of upper rotor assembly 28 and the lower rotor assembly 32 may be the same or different.

Another feature to reduce pilot workload includes automatically adjusting the RPM and/or pitch of propeller 42 in response to a velocity or acceleration command from the pilot. Conventional systems would require the pilot to adjust propeller RPM and/or pitch through individual inputs. The flight control system 120 allows the pilot to enter a desired velocity or acceleration, and the FCC 124 generates the proper control commands to the translational thrust interface 130 and the engine interface 133 to establish an RPM and/or pitch to meet the desired velocity or acceleration.

In exemplary embodiments, the flight control system 120 controls the main rotor assembly 18 to prevent the tips of rotor blades 36 from exceeding a threshold speed. In exemplary embodiments, the threshold speed may be 0.9 Mach 1. This threshold would prevent the rotor blade tips from exceeding the speed of sound. The threshold speed may vary, and may be set to limit drag on the rotor blades to below a certain level. In one embodiment, the FCC 124 determines air temperature from sensors 122. FCC 124 may also determine prevailing wind speed and direction from sensors 122. The FCC 124 then computes the threshold speed based on the speed of sound (e.g., Mach 1) at the sensed air temperature. The FCC 124 may set the threshold to 0.9 Mach 1, for example. FCC 124 then controls RPM of the main rotor assembly 18 to prevent the rotor blade tips from exceeding the threshold. In an exemplary embodiment, the FCC maintain 85% of the nominal rotor RPM. FCC 124 may take into account prevailing wind direction and speed in controlling the RPM of the main rotor assembly 18. The 0.9 Mach 1 threshold is only one example, and other speed thresholds may be employed to achieve desired results (e.g., reduce drag).

In exemplary embodiments, active elevator 43 is configured and controlled to compensate for propeller torque and/or rotor downwash. Elevator 43 includes a left elevator and a right elevator on opposite sides of the axis of rotation of the propeller 42. The left elevator and right elevator may be independently controlled to assume different positions. The elevator and rudder actuation interface 132 is configured to receive commands from the FCC 124 to control one or more actuators, such as a mechanical-hydraulic or electric actuators, to position the left elevator and right elevator independently. This independent control of the left elevator and right elevator aids in compensating propeller torque and/or rotor downwash.

The left elevator and right elevator may also have different physical configurations to compensate for compensating propeller torque and/or rotor downwash. The left elevator and right elevator may be offset relative to each other along the longitudinal and/or lateral axes of aircraft 10. Further, the left elevator and right elevator may have different geometries where one of the left elevator and right elevator is larger than then other along the longitudinal and/or lateral axes of aircraft 10. The left elevator and right elevator may have differing aerodynamic surfaces (e.g., airfoils) as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. While the description has been presented for purposes of illustration and description, it is not intended to be exhaustive or limited. Many modifications, variations, alterations, substitutions, or equivalent arrangements not hereto described will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the description. Additionally, while the various embodiments have been described, it is to be understood that aspects may include only some of the described embodiments. 

What is claimed is:
 1. An aircraft comprising: an airframe; an extending tail; a counter rotating, coaxial main rotor assembly including an upper rotor assembly and a lower rotor assembly; a translational thrust system positioned at the extending tail, the translational thrust system providing translational thrust to the airframe; at least one sensor and at least one inertial measurement unit (IMU) to sense current flight conditions of the aircraft; an interface to execute controls of a main rotor assembly in accordance with control commands; and at least one flight control computer (FCC) to issue the control commands and comprising a central processing unit (CPU) and a memory having logic and executable instructions stored thereon, which, when executed, cause the CPU to issue the control commands based on the current flight conditions and a result of an execution of the logic for the current flight conditions.
 2. The aircraft according to claim 1, wherein the current flight conditions comprise a speed of the aircraft.
 3. The aircraft according to claim 2, wherein the interface comprises a rotor interface, which is coupled to upper and lower rotor assemblies of the main rotor assembly and configured to independently control collective and cyclic pitching thereof.
 4. The aircraft according to claim 3, wherein the logic comprises at least one of a fly-by-wire (FBW) or smart-control database and an algorithm.
 5. The aircraft according to claim 4, wherein: the FBW or smart-control database indexes the speed of the aircraft to control commands for setting respective collective pitching of the upper and lower rotor assemblies, and the algorithm computes control commands for setting respective collective pitching of the upper and lower rotor assemblies.
 6. A fly-by-wire (FBW) or smart-control system of a coaxial, counter-rotating aircraft, the FBW or smart-control system comprising: at least one sensor and at least one inertial measurement unit (IMU) to sense current flight conditions of the aircraft; interfaces to respectively execute controls of a main rotor assembly, a translational thrust system, controllable surfaces and an engine in accordance with respective control commands; and at least one flight control computer (FCC) to issue the control commands and comprising a central processing unit (CPU) and a memory having logic and executable instructions stored thereon, which, when executed, cause the CPU to issue the control commands based on the current flight conditions and a result of an execution of the logic for the current flight conditions.
 7. The FBW or smart-control system according to claim 6, wherein the current flight conditions comprise a speed of the aircraft.
 8. The FBW or smart-control system according to claim 7, wherein the interfaces comprise: a rotor interface, which is coupled to upper and lower rotor assemblies of the main rotor assembly and configured to independently control collective and cyclic pitching thereof; a translational thrust interface, which is coupled to the translational thrust system to control collective pitch or a power setting of the translational thrust system; an elevator and rudder actuation interface, which is coupled to active elevators and active rudders to control an angling thereof; an engine interface, which is coupled to the engine to control an RPM thereof; and a propeller clutch interface which is coupled to the propeller clutch to control the propeller engagement state.
 9. The FBW or smart-control system according to claim 8, wherein the logic comprises at least one of an FBW or smart-control database and an algorithm.
 10. The FBW or smart-control system according to claim 9, wherein the FBW or smart-control database indexes the speed of the aircraft to control commands for setting respective collective pitching of the upper and lower rotor assemblies.
 11. The FBW or smart-control system according to claim 9, wherein the algorithm computes control commands for setting respective collective pitching of the upper and lower rotor assemblies.
 12. The FBW or smart-control system according to claim 9, wherein the logic generates: differential collective pitch control commands for setting respective collective pitching of the upper and lower rotor assemblies in an event the speed of the aircraft is below a first speed; a mix of differential collective and differential cyclic pitch control commands for setting respective collective and cyclic pitching of the upper and lower rotor assemblies in an event the speed of the aircraft is above the first speed and below a second speed; and angle control commands for setting an angling of the active rudders in an event the speed of the aircraft is above the second speed.
 13. The FBW or smart-control system according to claim 9, wherein the logic generates envelope control commands for applying respective control envelopes to the upper and lower rotor assemblies.
 14. The FBW or smart-control system according to claim 9, wherein the logic generates a single control command for setting engine RPMs and collective pitch or a power setting of the translational thrust system.
 15. The FBW or smart-control system according to claim 9, wherein the logic generates a control command for setting an RPM schedule to maintain a predefined mach number of the upper and lower rotor assemblies. 